home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93b.txt
/
000128_icon-group-sender _Mon May 31 21:53:19 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-06-16
|
2KB
Received: from owl.CS.Arizona.EDU by cheltenham.CS.Arizona.EDU; Sat, 5 Jun 1993 18:52:17 MST
Received: by owl.cs.arizona.edu; Sat, 5 Jun 1993 18:52:16 MST
Date: 31 May 93 21:53:19 GMT
From: mercury.hsi.com!mlfarm!auda!ron@uunet.uu.net (Ronald Florence)
Organization: Maple Lawn Farm, Stonington, CT
Subject: Re: Icon on a mixed-architecture network
Message-Id: <1993May31.215319.710@mlfarm.com>
References: <199305311843.AA02129@chuckwalla.cs.arizona.edu>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
"Clint Jeffery" writes:
In addition to the executable header and byte-order issues which you've
already thought of, there are at least two more potential problems that
come to mind:
1) word alignment: I believe Sparcs are longword aligned.
2) C structure layout: icode includes various data in C
structure format, and the icont and iconx had better
agree on what they look like in memory.
To my astonishment and delight, the same executables work on both
architectures (sparc and sun3). I use the compact headers on Icon
executables
#!/usr/local/bin/iconx
and have the PATH environmental variables set up so a user on any
machine gets the appropriate iconx. We put icon executables, along
with shell scripts, in /usr/local/share/bin, which is shared by sparc
and m68030 machines.
Another big plus for Icon...
--
Ronald Florence
ron@mlfarm.com